Skip to content

Add enterprise page#545

Open
madhuramendis wants to merge 4 commits intoopenchoreo:mainfrom
madhuramendis:main
Open

Add enterprise page#545
madhuramendis wants to merge 4 commits intoopenchoreo:mainfrom
madhuramendis:main

Conversation

@madhuramendis
Copy link
Copy Markdown
Contributor

Purpose

Briefly describe what this pull request does.

Related Issues

Include any related issues that are resolved by this PR.

Checklist

  • Updated sidebars.ts if adding a new documentation page
  • Run npm run start to preview the changes locally
  • Run npm run build to ensure the build passes without errors
  • Verified all links are working (no broken links)

Signed-off-by: Madhura Mendis <madhuramendis@gmail.com>
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Apr 6, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 58065bf2-b394-42a2-af1c-3a7af1f37ed2

📥 Commits

Reviewing files that changed from the base of the PR and between a59b716 and 1c6b1d3.

📒 Files selected for processing (1)
  • src/clientModules/gtagGuard.ts
✅ Files skipped from review due to trivial changes (1)
  • src/clientModules/gtagGuard.ts

📝 Walkthrough

Summary by CodeRabbit

  • New Features
    • Added an "Enterprise" link to the main navigation.
    • Launched an Enterprise page with hero, offering cards, feature lists, responsive styling, and a "Learn More" external link.
  • Bug Fixes
    • Improved site stability by guarding analytics to prevent runtime errors during navigation.

Walkthrough

Adds a new Enterprise site page with associated styles, registers a client-side gtag guard module, and updates the navbar to include a left-positioned "Enterprise" link in the Docusaurus config.

Changes

Cohort / File(s) Summary
Docusaurus configuration
docusaurus.config.ts
Imported Node path, added clientModules entry to load src/clientModules/gtagGuard.ts on the client, and added a left-positioned Enterprise navbar link to /enterprise.
Enterprise page & styles
src/pages/enterprise.tsx, src/pages/enterprise.module.css
Added new /enterprise React page (default export) rendering a hero and an offering card with provider logo, tagline, mapped feature list, and an external "Learn More" link; added CSS module with layout, card, feature/icon, button styles, dark-theme overrides, and responsive rules.
Client-side guard
src/clientModules/gtagGuard.ts
Added client module that ensures window.gtag is a no-op function when missing to prevent runtime errors during route changes.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The description uses the correct template structure but is entirely empty—Purpose and Related Issues sections contain only placeholders with no actual content filled in. Fill in the Purpose section with a brief description of the enterprise page's purpose and any Related Issues this PR addresses. The checklist can remain as-is for author verification.
✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately summarizes the main change: a new enterprise page is added to the project with corresponding configuration and styling.
Docstring Coverage ✅ Passed Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@src/pages/enterprise.module.css`:
- Around line 137-139: The current CSS rule .cButton:focus { outline: none; }
removes keyboard focus visibility and must be replaced with a visible,
accessible focus style; update the selector to use .cButton:focus-visible (or
keep :focus for broader support) and add a clear high-contrast focus indicator
(for example a 2px solid outline or visible box-shadow and outline-offset) that
uses an accessible color token (e.g., --focus-color) so keyboard users can see
focus on the CTA button; ensure you remove the outline:none rule and add the new
focus style to the .cButton ruleset.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: e8738ea5-9e90-4eb6-9ed7-cd76ec8fe080

📥 Commits

Reviewing files that changed from the base of the PR and between 5225390 and bd7bae0.

📒 Files selected for processing (3)
  • docusaurus.config.ts
  • src/pages/enterprise.module.css
  • src/pages/enterprise.tsx

Comment on lines +137 to +139
.cButton:focus {
outline: none;
}
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Do not remove keyboard focus visibility on the CTA button.

Line 137-Line 139 removes focus outline with no replacement, which is an accessibility regression for keyboard users.

💡 Proposed fix
-.cButton:focus {
-  outline: none;
-}
+.cButton:focus-visible {
+  outline: 2px solid var(--ifm-color-primary);
+  outline-offset: 2px;
+}
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
.cButton:focus {
outline: none;
}
.cButton:focus-visible {
outline: 2px solid var(--ifm-color-primary);
outline-offset: 2px;
}
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@src/pages/enterprise.module.css` around lines 137 - 139, The current CSS rule
.cButton:focus { outline: none; } removes keyboard focus visibility and must be
replaced with a visible, accessible focus style; update the selector to use
.cButton:focus-visible (or keep :focus for broader support) and add a clear
high-contrast focus indicator (for example a 2px solid outline or visible
box-shadow and outline-offset) that uses an accessible color token (e.g.,
--focus-color) so keyboard users can see focus on the CTA button; ensure you
remove the outline:none rule and add the new focus style to the .cButton
ruleset.

@Mirage20 Mirage20 requested a review from sameerajayasoma April 6, 2026 13:04
Signed-off-by: Madhura Mendis <madhuramendis@gmail.com>
Signed-off-by: Madhura Mendis <madhuramendis@gmail.com>
Signed-off-by: Madhura Mendis <madhuramendis@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant